<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>65. Part</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="PART">PART</h1>
		<h3 id="DEFINITION">DEFINITION</h3>
		<p>Parts for Components are similar to Properties for Classes. They allow reusing Component definitions (Type) in several contexts.</p>
		<p>Parts help defining assembly of Components. Parts might have cardinalities.</p>
		<p>Note: Parts should not be used when following the Arcadia methodology, as Components in that case are considered as unique Instances. Reuse in Arcadia is managed with Model Patterns.</p>
		<h3 id="ICONS">ICONS</h3>
		<p>
			<img height="66" width="75" border="0" src="Images/65.%20Part_html_19bbfed7.png"/>
			<img height="66" width="75" border="0" src="Images/65.%20Part_html_m79fce328.png"/>
			<img height="66" width="75" border="0" src="Images/65.%20Part_html_282e0220.png"/>
			<img height="66" width="75" border="0" src="Images/65.%20Part_html_m4d022fd7.png"/>
		</p>
		<p>
			<br/>

			<br/>
		</p>
		<p>
			<br/>
		</p>
	</body>
</html>